https://github.com/rust-lang/rfcs/pull/1133#issuecomment-230950635

Cargo cannot express dependencies on "A compiler with support for X." This affects far more > than just the sysroot - every crate that uses a feature that went through stabilization post 1.0 should make use of such a thing. The sysroot getting a free pass on this papers over it just enough that it remains unfixed and painful for everyone else, IMO.
The sysroot uses unstable features internally, because it knows the rustc version it is built with. This is both a subset of the above, and hostile to independent compiler implementations. A principled solution to the above could easily encompass the unstable features used (heck, Cabal manages it!).
Not needing to recompile it for each crate. This is something that could be amply solved in the general case by Cargo keeping some global cache of built crates indexed by target, version, and features.

they mention cabal specifically and frequently. i suspect simon peyton-jones's involvement

My London-based client is looking for a senior software engineer with Extreme Programming experience on the JVM - ideally in Kotlin.

Established Open Source start-up with real customers and US backing, working on developer tools you may have heard of.

Salary range: £90K-£120K.

Hybrid, 2 days/week on site in central London.

You must be eligible to work in the UK.

"Pour Timothé, militant de 28 ans dans le Loiret, « le premier combat des socialistes, c’est l’antifascisme », et il se félicite de voir des associations le porter. « Il y a SOS Racisme, qui est un outil fondamental pour la lutte contre le racisme et dont le propos est plus d’actualité que jamais », assure-t-il."

#Presidentielle2027 #PartiSocialiste #antifa

Le PS fait sa rentrée à Blois avec des débats sans risque dans l’attente de la primaire
https://www.mediapart.fr/journal/politique/290826/le-ps-fait-sa-rentree-blois-avec-des-debats-sans-risque-dans-l-attente-de-la-primaire

Given the same talk since 2020, people love to turn an archive into a hostage situation

https://jon-e.net/infrastructure-presentation/?slideIndex=3

By desugaring stdlib dependencies this early in the pipeline, we
are able to touch much less of Cargo. On the other hand, "stdlib"
is no longer a valid version for the purpose of [[replace]]-ing.

https://github.com/rust-lang/rfcs/pull/1133#issuecomment-223746363

This isn't so bad, because one can still replace the dep the if one
knows the version number of the normally-resolved stdlib version.
More philosophically, replacements are done after solving version
requirements, at which point version requirements are gone and only
concrete resolved versions remain. "stdlib", in delegating the
choice of version elsewhere, is thus more of a version requirement
than version.

Lol. Why not. I hope it's really terrifically awful and we all love it. Might be the making of him.

@Rubelicious agree; the https://staygold.us project is a part of that, but if anyone is in NYC (or most large major cities) I don't know what to do..

are they wearing kevlar?

@thefathippy @ascentale @bikenite and Boris Fucking Johnson

Am I correct that as a side effect of this, cargo will learn to download sources of standard library crates? This will be super useful for IDE integration :)

https://github.com/rust-lang/rfcs/pull/1133#issuecomment-214361711

@matklad Yes it would, but only when it builds them from source as currently written. Of course, that can be changed however so it downloads it more often---that could be useful for overcoming the override limitations too.

@kepano Some ideas:

Aerial : https://f-droid.org/packages/com.shapeshed.aerial

Bmihi music : https://apt.izzysoft.de/packages/ca.ilianokokoro.umihi.music

Chocola : https://f-droid.org/packages/com.sosauce.cutemusic

Grit : https://f-droid.org/packages/com.shub39.grit

Lune : https://f-droid.org/packages/com.demonlab.lune

Musify : https://f-droid.org/packages/com.gokadzev.musify.fdroid

vivi : https://apt.izzysoft.de/packages/com.vivi.vivimusic

@roadriverrail in this timeline, who the hell knows, legit concern

The legal term 'terrorism' is changing; now in Scotland protestors who spray painted a club house at a golf club & dug up some grass have had their charges linked to a 'terrorist connection'....

Of course, this may be due to the owner of the golf course (the Tangerine Tyrant), but once vandalism becomes regularly linked to 'terrorism' in courts, the impact on the right to protest is pretty clear.

Its one more move against democracy in the UK!

#protest #politics
https://www.theguardian.com/uk-news/2026/aug/28/seven-charged-damaging-trump-scottish-golf-course-accused-terrorist-connection

No matter what you believe about yourself, having The Atlantic rigorously catalog what a **** you are must be rough.

Nice pic. (credit: Win McNamee)

https://www.theatlantic.com/ideas/2026/08/karoline-leavitt-press-secretary-lies/688460/?gift=xKut_ZEsKKc2fxSPw_DukxATocxtEAqgiMfqWKtOQSE&utm_source=copy-link&utm_medium=social&utm_campaign=share

@david_chisnall @dysfun I am from the home country of the Pumpernickel...what can I say?🤷🏻‍♂️

https://en.wikipedia.org/wiki/Pumpernickel

There is a "pure" subset of the standard library that Cargo was born knowing how to compile

consider this statement

@thomasfuchs WTF is even this feature ?

AHA IT'S WORKING

(the relay actor thingy, not the pee; well, that was already working)

Again the Green Party of England & Wales & the (so-called) Labour Party, are on opposite sides of an issue that is prominent on Mastodon:

Andy Burnham's administration has rejected Zack Polanski's calls to pause the construction (and planning clearances) for data centres in the UK, which are increasingly obvious threats both to the environment & to water supplies wherever they are built.

Handy if you were unsure whose side Labour were on....

#DataCentres #AI #politics
https://www.theguardian.com/uk-news/2026/aug/28/labour-green-party-zack-polanski-ai-datacentres

https://github.com/rust-lang/rfcs/pull/1133#issuecomment-164532576

To elaborate, the work beyond this RFC for that is

• Sign stdlib source code per stable compiler
• Teach stable rustc how to check to see if inputs match whitelist of signatures
• Cargoize the stdlib (we both already did that, right?)
• Teach Cargo how to find stdlib source per stable compiler including Cargofiles. Or just include source with stable compiler binary release

For those cross-compiling to a fixed few "conventional platforms", it may just be easier to download binaries for the foreign deps, or yes, even the rust libs too. I've argued against this in the RFC, thread, on IRC. But in hindsight, we really need not take an either-or approach. There is a "pure" subset of the standard library that Cargo was born knowing how to compile, and there is the whole extent which will always have some non-Rust deps (until somebody wants to support re-wrapping the the OS ABIs in pure Rust shims). I think it probably makes sense to keep this RFC focused on compiling the trivial subset since the two methodologies are indeed so different, but I'd be happy to help design/implement the binary download stuff too. Over time I still maintain the approaches can and should grow together, but to start it might be easiest to pursue both independently.